[SLO] Stabilize deployment-agnostic SLO cleanup deletion#253726
Merged
fkanout merged 2 commits intoelastic:mainfrom Feb 18, 2026
Merged
[SLO] Stabilize deployment-agnostic SLO cleanup deletion#253726fkanout merged 2 commits intoelastic:mainfrom
fkanout merged 2 commits intoelastic:mainfrom
Conversation
Switch deleteAllSLOs in deployment-agnostic API tests from parallel deletion to sequential deletion to reduce teardown contention and transient 500 responses. Co-authored-by: Cursor <cursoragent@cursor.com>
github-actions
Bot
added
the
author:actionable-obs
fkanout
added
backport:version
Contributor
|
Pinging @elastic/actionable-obs-team (Team:actionable-obs) |
dmlemeshko
approved these changes
Feb 18, 2026
Contributor
⏳ Build in-progress, with failures
Failed CI StepsHistory |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#10780[✅] x-pack/solutions/observability/test/api_integration_deployment_agnostic/configs/serverless/oblt.serverless.config.ts: 50/50 tests passed. |
Contributor
|
Starting backport for target branches: 9.3 https://github.com/elastic/kibana/actions/runs/22149647298 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Feb 18, 2026
) ## Summary It fixes elastic#252819 - Change deployment-agnostic SLO test cleanup (`deleteAllSLOs`) from parallel deletes to sequential deletes. - Keep existing strict `204` expectation for each delete request. - Reduce teardown contention that can surface as intermittent `500` errors during cleanup. ## Why `deleteAllSLOs` is used heavily in deployment-agnostic API integration setup/teardown. Running all SLO deletions in parallel can overload transform/rule/data cleanup in CI and produce transient failures. Sequential deletion improves stability while preserving coverage and assertions. ## Files changed - `x-pack/solutions/observability/test/api_integration_deployment_agnostic/services/slo_api.ts` ## Test plan - [x] Lint check for edited file - [ ] Run deployment-agnostic SLO API integration suite in CI Made with the help of [Cursor](https://cursor.com) (cherry picked from commit adf6d7d)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
This was referenced Feb 18, 2026
kibanamachine
added a commit
that referenced
this pull request
Feb 18, 2026
…) (#253775) # Backport This will backport the following commits from `main` to `9.3`: - [[SLO] Stabilize deployment-agnostic SLO cleanup deletion (#253726)](#253726) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Faisal Kanout","email":"faisal.kanout@elastic.co"},"sourceCommit":{"committedDate":"2026-02-18T17:07:12Z","message":"[SLO] Stabilize deployment-agnostic SLO cleanup deletion (#253726)\n\n## Summary\n\nIt fixes https://github.com/elastic/kibana/issues/252819\n\n- Change deployment-agnostic SLO test cleanup (`deleteAllSLOs`) from\nparallel deletes to sequential deletes.\n- Keep existing strict `204` expectation for each delete request.\n- Reduce teardown contention that can surface as intermittent `500`\nerrors during cleanup.\n\n## Why\n`deleteAllSLOs` is used heavily in deployment-agnostic API integration\nsetup/teardown. Running all SLO deletions in parallel can overload\ntransform/rule/data cleanup in CI and produce transient failures.\nSequential deletion improves stability while preserving coverage and\nassertions.\n\n## Files changed\n-\n`x-pack/solutions/observability/test/api_integration_deployment_agnostic/services/slo_api.ts`\n\n## Test plan\n- [x] Lint check for edited file\n- [ ] Run deployment-agnostic SLO API integration suite in CI\n\n\nMade with the help of [Cursor](https://cursor.com)","sha":"adf6d7d84e78e061b3b6505dae647a4475091878","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:actionable-obs","backport:version","v9.3.0","v9.4.0","author:actionable-obs"],"title":"[SLO] Stabilize deployment-agnostic SLO cleanup deletion","number":253726,"url":"https://github.com/elastic/kibana/pull/253726","mergeCommit":{"message":"[SLO] Stabilize deployment-agnostic SLO cleanup deletion (#253726)\n\n## Summary\n\nIt fixes https://github.com/elastic/kibana/issues/252819\n\n- Change deployment-agnostic SLO test cleanup (`deleteAllSLOs`) from\nparallel deletes to sequential deletes.\n- Keep existing strict `204` expectation for each delete request.\n- Reduce teardown contention that can surface as intermittent `500`\nerrors during cleanup.\n\n## Why\n`deleteAllSLOs` is used heavily in deployment-agnostic API integration\nsetup/teardown. Running all SLO deletions in parallel can overload\ntransform/rule/data cleanup in CI and produce transient failures.\nSequential deletion improves stability while preserving coverage and\nassertions.\n\n## Files changed\n-\n`x-pack/solutions/observability/test/api_integration_deployment_agnostic/services/slo_api.ts`\n\n## Test plan\n- [x] Lint check for edited file\n- [ ] Run deployment-agnostic SLO API integration suite in CI\n\n\nMade with the help of [Cursor](https://cursor.com)","sha":"adf6d7d84e78e061b3b6505dae647a4475091878"}},"sourceBranch":"main","suggestedTargetBranches":["9.3"],"targetPullRequestStates":[{"branch":"9.3","label":"v9.3.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/253726","number":253726,"mergeCommit":{"message":"[SLO] Stabilize deployment-agnostic SLO cleanup deletion (#253726)\n\n## Summary\n\nIt fixes https://github.com/elastic/kibana/issues/252819\n\n- Change deployment-agnostic SLO test cleanup (`deleteAllSLOs`) from\nparallel deletes to sequential deletes.\n- Keep existing strict `204` expectation for each delete request.\n- Reduce teardown contention that can surface as intermittent `500`\nerrors during cleanup.\n\n## Why\n`deleteAllSLOs` is used heavily in deployment-agnostic API integration\nsetup/teardown. Running all SLO deletions in parallel can overload\ntransform/rule/data cleanup in CI and produce transient failures.\nSequential deletion improves stability while preserving coverage and\nassertions.\n\n## Files changed\n-\n`x-pack/solutions/observability/test/api_integration_deployment_agnostic/services/slo_api.ts`\n\n## Test plan\n- [x] Lint check for edited file\n- [ ] Run deployment-agnostic SLO API integration suite in CI\n\n\nMade with the help of [Cursor](https://cursor.com)","sha":"adf6d7d84e78e061b3b6505dae647a4475091878"}}]}] BACKPORT--> Co-authored-by: Faisal Kanout <faisal.kanout@elastic.co>
chrisbmar
pushed a commit
to chrisbmar/kibana
that referenced
this pull request
Feb 19, 2026
) ## Summary It fixes elastic#252819 - Change deployment-agnostic SLO test cleanup (`deleteAllSLOs`) from parallel deletes to sequential deletes. - Keep existing strict `204` expectation for each delete request. - Reduce teardown contention that can surface as intermittent `500` errors during cleanup. ## Why `deleteAllSLOs` is used heavily in deployment-agnostic API integration setup/teardown. Running all SLO deletions in parallel can overload transform/rule/data cleanup in CI and produce transient failures. Sequential deletion improves stability while preserving coverage and assertions. ## Files changed - `x-pack/solutions/observability/test/api_integration_deployment_agnostic/services/slo_api.ts` ## Test plan - [x] Lint check for edited file - [ ] Run deployment-agnostic SLO API integration suite in CI Made with the help of [Cursor](https://cursor.com)
ersin-erdal
pushed a commit
to ersin-erdal/kibana
that referenced
this pull request
Feb 19, 2026
) ## Summary It fixes elastic#252819 - Change deployment-agnostic SLO test cleanup (`deleteAllSLOs`) from parallel deletes to sequential deletes. - Keep existing strict `204` expectation for each delete request. - Reduce teardown contention that can surface as intermittent `500` errors during cleanup. ## Why `deleteAllSLOs` is used heavily in deployment-agnostic API integration setup/teardown. Running all SLO deletions in parallel can overload transform/rule/data cleanup in CI and produce transient failures. Sequential deletion improves stability while preserving coverage and assertions. ## Files changed - `x-pack/solutions/observability/test/api_integration_deployment_agnostic/services/slo_api.ts` ## Test plan - [x] Lint check for edited file - [ ] Run deployment-agnostic SLO API integration suite in CI Made with the help of [Cursor](https://cursor.com)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
It fixes #252819
deleteAllSLOs) from parallel deletes to sequential deletes.204expectation for each delete request.500errors during cleanup.Why
deleteAllSLOsis used heavily in deployment-agnostic API integration setup/teardown. Running all SLO deletions in parallel can overload transform/rule/data cleanup in CI and produce transient failures. Sequential deletion improves stability while preserving coverage and assertions.Files changed
x-pack/solutions/observability/test/api_integration_deployment_agnostic/services/slo_api.tsTest plan
Made with the help of Cursor